home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group02b.txt
/
000123_icon-group-sender_Tue Nov 19 16:36:20 2002.msg
< prev
next >
Wrap
Internet Message Format
|
2003-01-02
|
3KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.11.1/8.11.1) id gAJNaFw19778
for icon-group-addresses; Tue, 19 Nov 2002 16:36:15 -0700 (MST)
Message-Id: <200211192336.gAJNaFw19778@baskerville.CS.Arizona.EDU>
From: Christopher Browne <cbbrowne@acm.org>
X-Newsgroups: comp.lang.icon
Subject: Re: I know why Icon isn't popular.
Date: 19 Nov 2002 23:28:53 GMT
X-Draft-From: ("nntp+chvatal:comp.lang.icon" 197)
X-Home-Page: http://www.cbbrowne.com/info/
X-Emacs-Acronym: Every Mode Acknowledges Customized Strokes
Microsoft: We've got the solution for the problem we sold you.
X-Uboat-Death-Message: BOMBED BY IRC SERVER. SINKING. U-14.
To: icon-group@cs.arizona.edu
Errors-To: icon-group-errors@cs.arizona.edu
Status: RO
The world rejoiced as jleger@afslogistics.com (Jonathan Leger) wrote:
> But Icon lacks the tools and technologies needed by real-world
> applications programmers, at least in the Windows world. It does not
> have (or at least I am not aware of it having):
>
> 1) A strong IDE.
> 2) A strong visual GUI developer.
> 3) Built-in real-world database support (though Unicon took care of
> this with ODBC).
>
> To be accepted into the world of Windows application programmers, Icon
> needs:
>
> 4) Support for technologies like COM+.
> 5) The ability to compile Icon libraries to DLLs for use in other
> languages.
In the Unix world, the /lack/ of all of those things is generally
considered a /benefit/, and if those technologies were added to Icon,
that would almost certainly make it look /less attractive/ to the very
sorts of people that would be more likely to consider Icon than the
"Windows flunkies."
And before you dismiss that as a bigoted statement (which, to a goodly
degree, it is), ask yourself if Microsoft is likely to add Icon into
its "official tool set."
The answer is "not bloody likely."
The sorts of folks that are a /lot/ more likely to be accepting of
Icon are more likely to be "Unix fans" that will fall into the
"bigoted" group that would agree with my first paragraph...
Note that /everyone/ is a bigot, in this context, whether we're
talking about:
a) Windows bigots, that would regard any deployment of Icon that
/wasn't/ bundled as "Official Microsoft(tm) VisualIcon Studio" as
being futile because no /real/ programmer could /possibly/ get any
work done without their "VisualIcon Studio," or
b) Unix bigots that regard things the exact opposite way...
Since it is /totally/ improbable that Microsoft will be replacing
VB.Net with "VisualIcon Studio," I suggest that you're better off
trying to sell Icon to the Unix bigots...
--
(reverse (concatenate 'string "moc.enworbbc@" "enworbbc"))
http://www3.sympatico.ca/cbbrowne/languages.html
Oh, no. Not again.
-- a bowl of petunias